- Remove unused datetime imports (timezone, timedelta) from connector.py
  introduced when lag_minutes was removed
- Wrap all E501 log message f-strings across api.py, backfill.py,
  connector.py, incremental.py, and pre_sync_drift_check.py
- Apply black reformatting to utils.py (INCREMENTAL_CHECKPOINT_INTERVAL_SECONDS)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Black always generates W503-style line breaks (operator at start of
continuation line). Without this, any connector using multi-line boolean
conditions will fail the linting check. W503 and W504 are mutually
exclusive — suppressing W503 is the standard fix for Black + flake8
coexistence.

Also removes noqa: W503 comments added as a temporary workaround.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

The comments were adding enough length to trigger Black reformatting.
W503 is now globally ignored via .flake8 so the comments are redundant.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Add template-style import comments to connector.py and api.py
- Replace update() docstring with verbatim template wording
- Add log.warning("Example: Oracle WMS : wms_oracle") as first log in update()
- Replace single-line upsert comment with full template comment block
- Add template checkpoint comment block before op.checkpoint()
- Add template __main__ block comments
- Add full Description/Args/Returns docstrings to check_entity_has_mod_ts and probe_entity_count
- Add retry logic (408, 429, 500-504, Timeout) to check_entity_has_mod_ts
- Replace literal defaults in configuration.json and README with angle-bracket placeholders
- Add numbered credential-setup steps to README Authentication section

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

- Add full Description/Args/Returns/Raises to make_api_request and fetch_entity_data
- Refactor multi-line boolean conditions into intermediate variables to eliminate
  W503 (line-break-before-binary-operator) violations without flake8 suppression

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Replace chained variable assignments with clearer named variables and
explicit break conditions, eliminating W503 violations without flake8
suppression.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…nt log

- Refactor multi-line boolean conditions in backfill.py and incremental.py
  into named variables to eliminate W503 without flake8 suppression
- Simplify string concatenation in connector.py log statement
- Remove redundant log.info after log.warning example banner in update()

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…ckfill

Replace two-line ts_boundary_cleared assignment with a single readable
line using short-circuit evaluation, and rename to crossed_ts_boundary.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

… by Pass 1

All incremental_only entities have an incremental cursor (required by
classification), so they are always included in entities_with_cursor and
processed in Pass 1. Pass 3 could never execute.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Worker threads in the backfill pass now do API fetching only, putting
upsert/truncate/checkpoint messages on a queue.Queue. The main thread
drains the queue and performs all op.* calls, complying with the SDK's
single-threaded output stream requirement.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Guard against any unexpected queue message format with a warning log
before unpacking. If a non-3-tuple arrives it is skipped and logged
rather than crashing the sync, so the next run reveals the exact
message that caused the original ValueError.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…_has_mod_ts

Returning False after all retries fail was silently caching an incorrect
mod_ts capability flag in state, causing repeated unnecessary full scans
and op.truncate() calls. Now raises on transient failures (408, 429,
5xx, Timeout) so the sync fails cleanly instead of poisoning the cache.
Permanent errors (non-transient status codes) still return False.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Permanent errors (auth failures, connection errors, non-transient HTTP
status codes) now also raise instead of returning False, so no describe
failure can silently cache an incorrect mod_ts capability in state.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

ConnectionError has no HTTP status code (status=None), so it bypassed
the transient_status_codes check and raised immediately without retrying.
Now any RequestException without a status code is treated as transient
and retried like 408/429/5xx.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>